Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tried to follow what @suaviloquence did when he added
lint_level
to the query.Some thoughts after taking more look into the issue:
should we introduce another field in the SemVerQuery called
lint_mode
which is an Enum to be eitherSemVer
orAlwaysRun
with default to beSemVer
? Or should we encapsulate therequired_update
field into this LintMode enum since when lint_mode isAlwaysRun
,RequiredSemverUpdate
seems meaningless? I am still in favor of the 1st one for better DX but the second one is more clear?We will run all need-to-run queries together, but when displaying the overall view should we seperate them? since before the category would be
major
/minor
now we havealways-run
example command output
Todo:
manifest_tests
?run mode
list
type fix